-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade mongodb-client to 5.1.3 #42445
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks!
I added some small questions inline.
BTW, if you feel like it and things are relatively straightforward, I'm all for removing the calls to deprecated methods.
It might be too involved though so feel free to not do it.
Probably a good idea to do it in a specific commit if you pursue this.
if (oplogReplay) { | ||
publisher = publisher.oplogReplay(true); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also drop the field/method in our class?
It doesn't have any replacement that we would need to support?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your attentiveness, yes we should drop the field. I'll take care of it.
According to the 4.11.1 Javadocs this option isn't supported on a database level from MongoDB 4.4 onwards.
No additional options were introduced between the versions.
private boolean sharded; | ||
private boolean nonAtomic; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are no replacement or additional fields we need to support?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the 4.11.1 Javadocs these two options aren't supported on a database level from MongoDB 4.4 onwards.
In comparison to 4.11.1 only those two fields were removed and none were added.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe there will be more work that needs to be invested in this area in the future.
The whole Map-Reduce functionality was deprecated in version 5.0 and should be replaced with aggregates.
See Map-Reduce.
removed the superfluous field. |
Sorry to be that guy but could you have a first line in the commit message saying it's the upgrade? (i.e. the title of the PR) |
No problem. |
Perfect. In general, no problem to add a lot more details to the message but the first line should be really the top level thing we are doing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Let's run CI and see how it goes.
Status for workflow
|
The extension compiles now, and the integration test runs successfully.
The following changes were necessary:
There were a couple of deprecations, that were ignored for too long and the corresponding classes/methods were removed in this or an earlier version of the mongoldb java client.
I believe there is still some work to do with the extension, because there are still more than 30 deprecation warnings during compilation.